Electronic device and communication method

ABSTRACT

A communication method of an application processor includes generating a plurality of files; generating a file set channel by transmitting a first pattern of input/output (I/O) requests to a storage device, the I/O requests being I/O requests corresponding to files from among the plurality of files; and transmitting first bit data to the storage device via the file set channel, the first bit data being transmitted using file set signaling, the file set signaling including a second pattern of I/O requests corresponding to first files from among the plurality of files such that each file in the plurality of files represents a bit of the first bit data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This U.S. non-provisional patent application is a continuation of U.S.application Ser. No. 14/628,598 filed on Feb. 23, 2015, which claimspriority under 35 U.S.C. §119 to Korean Patent Application No.10-2014-0021414 filed Feb. 24, 2014, the subject matter of each of whichis hereby incorporated by reference.

BACKGROUND

One or more example embodiments of the inventive concepts relate to anelectronic device, and more particularly, relate to a non-standardcommunication method of an electronic device.

Semiconductor memory devices may be classified into volatilesemiconductor memory devices and nonvolatile semiconductor memorydevices. The nonvolatile semiconductor memory devices may retain datastored therein even at power-off; on the other hand, data stored in thenonvolatile semiconductor memory device may be permanent orreprogrammable, depending upon the fabrication technology used. Thenonvolatile semiconductor memory devices may be used for user datastorage and program and microcode storage in a wide variety ofapplications in the computer, avionics, telecommunications, and consumerelectronics industries.

SUMMARY

According to one or more example embodiments, a communication method ofan application processor includes generating a plurality of files;generating a file set channel by transmitting a first pattern ofinput/output (I/O) requests to a storage device, the I/O requests beingI/O requests corresponding to files from among the plurality of files;and transmitting first bit data to the storage device via the file setchannel, the first bit data being transmitted using file set signaling,the file set signaling including a second pattern of I/O requestscorresponding to first files from among the plurality of files such thateach file in the plurality of files represents a bit of the first bitdata.

According to example embodiments, a communication method of a storagedevice includes receiving, from a host, first input/output (I/O)requests corresponding to a plurality of files; recognizing anon-standard communication based on the first I/O requests received;receiving second I/O requests on the plurality of files from the hostafter recognizing the non-standard communication; and interpreting thesecond I/O requests as bit data transmitted from the host.

According to example embodiments, a communication method of a hostincluding an application processor includes generating, at theapplication processor, a plurality of files; generating, at theapplication processor, a first pattern of input/output (I/O) requestssuch that the first pattern of I/O requests are recognizable by astorage device as a request to establish a file set channel between thehost and the storage device, the first pattern of I/O requests being I/Orequests corresponding to the plurality of files; establishing a fileset channel between the host and the storage device by transmitting thefirst pattern of I/O requests to the storage device; generating, at theapplication processor, a second pattern of I/O requests such that eachfile in the plurality of files represents a bit of bit data, the secondpattern of I/O requests being I/O requests corresponding to first filesfrom among the plurality of files; and transmitting the bit data to thestorage device via the file set channel by transmitting the secondpattern to the storage device.

BRIEF DESCRIPTION OF THE FIGURES

The above and other features and advantages of example embodiments ofthe inventive concepts will become more apparent by describing in detailexample embodiments of the inventive concepts with reference to theattached drawings. The accompanying drawings are intended to depictexample embodiments of the inventive concepts and should not beinterpreted to limit the intended scope of the claims. The accompanyingdrawings are not to be considered as drawn to scale unless explicitlynoted.

FIG. 1 is a block diagram schematically illustrating an electronicdevice for describing one or more example embodiments of the inventiveconcepts;

FIG. 2 is a diagram schematically illustrating software architecture fordescribing non-standard communication according to at least one exampleembodiment of the inventive concepts;

FIG. 3 is a diagram schematically illustrating software architectureaccording to one or more example embodiments of the inventive concepts;

FIG. 4 is a diagram schematically illustrating the non-standardcommunication protocol using a file set channel, according to at leastone example embodiment of the inventive concepts;

FIG. 5 is a diagram schematically illustrating the process of generatinga file set channel using a read request, according to at least oneexample embodiment of the inventive concepts;

FIG. 6 is a diagram showing a process of effectuating transmitting offile set signaling using a read request, according to at least oneexample embodiment of the inventive concepts;

FIG. 7 is a diagram schematically illustrating a method of effectuatingreceiving of file set signaling using a read request, according to atleast one example embodiment of the inventive concepts;

FIG. 8 is a diagram schematically illustrating non-standardcommunication using a write request, according to at least one exampleembodiment of the inventive concepts;

FIG. 9 is a diagram schematically illustrating non-standardcommunication using a write request, according to one or more exampleembodiments of the inventive concepts;

FIG. 10 is a diagram schematically illustrating non-standardcommunication using a write request, according to one or more exampleembodiments of the inventive concepts;

FIG. 11 is a flow chart schematically illustrating a non-standardcommunication of a host, according to at least one example embodiment ofthe inventive concepts;

FIG. 12 is a flow chart schematically illustrating a non-standardcommunication of a host, according to one or more example embodiments ofthe inventive concepts;

FIG. 13 is a flow chart schematically illustrating a non-standardcommunication of a host, according to one or more example embodiments ofthe inventive concepts;

FIG. 14 is a flow chart schematically illustrating a non-standardcommunication of a storage device, according to at least one exampleembodiment of the inventive concepts;

FIG. 15 is a flow chart schematically illustrating a method of executinga vendor command using file set signaling, according to at least oneexample embodiment of the inventive concepts;

FIG. 16 is a block diagram schematically illustrating a mobile deviceaccording to at least one example embodiment of the inventive concepts;

FIG. 17 is a block diagram schematically illustrating a mobile deviceaccording to one or more example embodiments of the inventive concepts;

FIG. 18 is a block diagram schematically illustrating a computing systemaccording to at least one example embodiment of the inventive concepts;

FIG. 19 is a block diagram schematically illustrating a solid statedrive according to at least one example embodiment of the inventiveconcepts;

FIG. 20 is a block diagram schematically illustrating an eMMC accordingto at least one example embodiment of the inventive concepts;

FIG. 21 is a block diagram schematically illustrating a UFS systemaccording to at least one example embodiment of the inventive concepts;and

FIG. 22 is a block diagram schematically illustrating a mobile deviceaccording to at least one example embodiment of the inventive concepts.

DETAILED DESCRIPTION

Detailed example embodiments of the inventive concepts are disclosedherein. However, specific structural and functional details disclosedherein are merely representative for purposes of describing exampleembodiments of the inventive concepts. Example embodiments of theinventive concepts may, however, be embodied in many alternate forms andshould not be construed as limited to only the embodiments set forthherein. Accordingly, while example embodiments of the inventive conceptsare capable of various modifications and alternative forms, embodimentsthereof are shown by way of example in the drawings and will herein bedescribed in detail. It should be understood, however, that there is nointent to limit example embodiments of the inventive concepts to theparticular forms disclosed, but to the contrary, example embodiments ofthe inventive concepts are to cover all modifications, equivalents, andalternatives falling within the scope of example embodiments of theinventive concepts. Like numbers refer to like elements throughout thedescription of the figures.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another. For example, a first element could be termed asecond element, and, similarly, a second element could be termed a firstelement, without departing from the scope of example embodiments of theinventive concepts. As used herein, the term “and/or” includes any andall combinations of one or more of the associated listed items. It willbe understood that when an element is referred to as being “connected”or “coupled” to another element, it may be directly connected or coupledto the other element or intervening elements may be present. Incontrast, when an element is referred to as being “directly connected”or “directly coupled” to another element, there are no interveningelements present. Other words used to describe the relationship betweenelements should be interpreted in a like fashion (e.g., “between” versus“directly between”, “adjacent” versus “directly adjacent”, etc.).

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of exampleembodiments of the inventive concepts. As used herein, the singularforms “a”, “an” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will be furtherunderstood that the terms “comprises”, “comprising,”, “includes” and/or“including”, when used herein, specify the presence of stated features,integers, steps, operations, elements, and/or components, but do notpreclude the presence or addition of one or more other features,integers, steps, operations, elements, components, and/or groupsthereof.

It should also be noted that in some alternative implementations, thefunctions/acts noted may occur out of the order noted in the figures.For example, two figures shown in succession may in fact be executedsubstantially concurrently or may sometimes be executed in the reverseorder, depending upon the functionality/acts involved.

Example embodiments of the inventive concepts are described herein withreference to schematic illustrations of idealized embodiments (andintermediate structures) of the inventive concepts. As such, variationsfrom the shapes of the illustrations as a result, for example, ofmanufacturing techniques and/or tolerances, are to be expected. Thus,example embodiments of the inventive concepts should not be construed aslimited to the particular shapes of regions illustrated herein but areto include deviations in shapes that result, for example, frommanufacturing.

An electronic device and a communication method according to at leastone example embodiment of the inventive concepts may effectuatenon-standard communication using file set signaling, regardless ofhardware restriction and software restriction. Here, the hardwarerestriction may mean what may not be defined by the standard interfacecommunication protocol of a storage device, and the software restrictionmay mean the situation where the standard protocol is not used due to alack of the authority of a running application even through the standardprotocol exists. Now will be described the file set signaling.

FIG. 1 is a block diagram schematically illustrating an electronicdevice 10 for describing one or more example embodiments of theinventive concepts. Referring to FIG. 1, an electronic device 10includes a storage device 100 and a host 200. Each of the storage device100 and the host 200 may include a processor. The term ‘processor’, asused herein, may refer to, for example, a hardware-implemented dataprocessing device having circuitry that is physically structured toexecute desired operations including, for example, operationsrepresented as code and/or instructions included in a program. Examplesof the above-referenced hardware-implemented data processing deviceinclude, but are not limited to, a microprocessor, a central processingunit (CPU), a processor core, a multiprocessor, an application-specificintegrated circuit (ASIC), and a field programmable gate array (FPGA).Further, according to one or more example embodiments of the inventiveconcepts, any or all the above-referenced processors may be implemented,for example, as a system on chip (SoC). All functions described hereinas being performed by the storage device 100 or host 200 may beperformed and/or controlled by the processors within the storage device100 and the host 200, respectively.

The storage device 100 stores data to be used in the host 200. Thestorage device 100 incorporates a non-standard communication determiner120 that determines non-standard communication based on input/outputrequests (e.g., write/read requests) for a plurality of files(hereinafter, referred to as a file set) from the host 200. Thenon-standard communication determiner 120 may be implemented any or allof hardware, software, and firmware forms. The non-standardcommunication determiner 120 recognizes a start of non-standardcommunication and converts the input/output requests for the file setinput after the start of the non-standard communication. Thenon-standard communication determiner 120 converts bit data to be sentto the host 200 after the start of the non-standard communication intopass/fail of an input/output request for a file set.

The host 200 encompasses an application 220 for executing non-standardcommunication with the storage device 100. For example, the application220 may be a magician program, which may be, for example, a program formanaging, monitoring, improving and/or optimizing the storage device100. The application 220 produces a plurality of files to generate/forma file set channel for non-standard communication and provides thestorage device 100 with a specific pattern of input/output requests forthe plurality of files, that is, a file set. The file set channel isformed if the non-standard communication determiner 120 recognizes aspecific pattern of input/output requests.

In accordance with the description above, the electronic device 10effectuates non-standard communication using the file set signaling.Here, the file set signaling may mean that each signal for input/outputrequests for each of files constituting a file set represent at leastone bit that is transmitted from the host 200 to the storage device 100,or vice versa. That is, the host 200 sends bit data to the storagedevice 100 via the file set channel, and the storage device 100transmits bit data to the host 200 via the file set channel.

FIG. 2 is a diagram schematically illustrating software architecture fordescribing non-standard communication according to at least one exampleembodiment of the inventive concepts. Referring to FIG. 2, a host 200includes a file system 210, an application 220, and a device driver 230.

The file system 210 may include, for example, any or all of anapplication programming interface (API), a file system manager, and adevice interface. Upon non-standard communication, the file system 210generates a plurality of files for forming a file set channel orinput/output requests for the plurality of files according to a requestof the application 220.

The device driver 230 provides the API for the file system 210 andconverts an access request (e.g., an input/output request) on hardware acommand which hardware (e.g., a storage device 100) can identify. Theaccess request may be issued by the file system 210.

According to one or more example embodiments of the inventive concepts,the file system 210 and the device driver 230 are included in anOperating System (OS), and the application 220 is installed on the OS.

The non-standard communication according to one or more exampleembodiments of the inventive concepts is effectuated as follows. First,“file io api” in which the application 220 is implemented may issue adisk input/output request “disk io” to the storage device 100. Examplesof the “file io api” include an api of CreateFile/ReadFile/WriteFile ina Windows operating system and api of open/read/write in a Linuxoperating system.

Next, a communication channel is configured between the application 220and the storage device 100 by generating a plurality of files (or, afile set), a file input/output request “file io” on a part of the fileset that the application 220 issues is generated, the file input/outputrequest “file io” is converted into a disk input/output request “diskio” by the OS and the file system 210, and the disk input/output request“disk io” is sent to the storage device 100. The storage device 100detects the disk input/output request “disk io” thus transmitted anddetermines a meaning of signals sent according non-standardcommunication. An example of non-standard communication involves usinginput/output read or write requests to transfer bits of data from thehost 200 to the storage device 100, or vice versa.

Then, addresses of files may not be changed in a general situation afterthe file set is produced. A specific task such as defragmentation causesa logical block addressing (LBA) change, but it is not carried out inthe situation where a file handle or descriptor is opened by theapplication 220. That an address is not changed after a file set isgenerated may mean that an address is not changed during file setsignaling between the application 220 and the storage device 100, andmay not mean that a logical block address is never changed.

Files to be used for the file set signaling may be irrelevant to whetherthe files have positions not related to each other, may not be storedbut generated if necessary, and may be deleted after the non-standardcommunication. Files constituting a file set according to the filesystem 210 may not exist in a contiguous area. The file system 210produces files constituting the file set by a cluster unit to allocatethe files to the number of sectors where continuity is secured.

The file set channel may be formed with intent to obtain information onthe same LBA between the application 220 and the storage device 100. Theapplication 220 need not know a logical block address directly, eventhough the application 220 can know a file name via the file system 210.The storage device 100 can know a logical block address that a diskinput/output request “disk io” issues and obtain a file name viaanalysis of a file system.

A manner of making a file set channel is a manner where a fileinput/output request “file io” with a specific pattern is issued fromthe application 220 with respect to N files constituting a communicationchannel and such a pattern is detected by a predetermined or,alternatively, desired storage device 100.

At least one example embodiment of the inventive concepts may supportthe non-standard communication using the file set signaling between theapplication 220 and the storage device 100.

In FIG. 2, the application 220 may effectuate the non-standardcommunication via the file system 210. However, one or more exampleembodiments of the inventive concepts are not limited thereto. Forexample, at least one example embodiment of the inventive concepts maybe changed or modified such that the non-standard communication isadditionally effectuated without passing through the file system 210.

FIG. 3 is a diagram schematically illustrating software architectureaccording to one or more example embodiments of the inventive concepts.Referring to FIG. 3, an application 220 a may effectuate firstnon-standard communication via a file system 210, which uses a file setchannel, and second non-standard communication via the file system 210,which does not use the file set channel. The first non-standardcommunication may be substantially the same as non-standardcommunication described with reference to FIG. 2, and a descriptionthereof is thus omitted.

The second non-standard communication is performed by transmitting acommand to a storage device 100 via a device driver 230 a. According toone or more example embodiments of the inventive concepts, the devicedriver 230 a may depend on an Operating System OS (e.g., Windows, Linux,MAC, Apple OS, Android, and so on).

The application 220 a is configured to effectuate one of the firstnon-standard communication and the second non-standard communication.For example, the second non-standard communication is set to a default,and the first non-standard communication is performed when the secondnon-standard communication is not effectuated. In contrast, the firstnon-standard communication is set to a default, and the secondnon-standard communication is performed when the first non-standardcommunication is not effectuated.

An electronic device 10 according to at least one example embodiment ofthe inventive concepts may support the first non-standard communicationusing the file system 210 and the second non-standard communication notusing the file system 210.

FIG. 4 is a diagram schematically illustrating the non-standardcommunication protocol using a file set channel, according to at leastone example embodiment of the inventive concepts. Referring to FIGS. 1to 3, when non-standard communication is required or, alternatively,desired, a host 200 generates a plurality of files and stores them in astorage device 100. The host 200 transmits a plurality of input/outputrequests with a predetermined or, alternatively, desired pattern on theplurality of files to the storage device 100, and the storage device 100recognizes the plurality of input/output requests with the predeterminedor, alternatively, desired pattern to form a file set channel fornon-standard communication (S10).

After the file set channel is formed, the host 200 and the storagedevice 100 communicate with each other via first and second file setsignaling. For example, the host 200 sends bit data to the storagedevice 100 via the first file set signaling (S20). Here, the first fileset signaling may consist of input/output requests (e.g., read/writerequests) for the plurality of files. At the first file set signaling, aread request or an update (or, write) request on a file is viewed as abit. Also, the storage device 100 parses bit data based on the firstfile set signaling from the host 200. That is, input/output requests onthe plurality of files transmitted from the host 200 may be parsed asbit data transferred from the host 200.

The storage device 100 transmits bit data to the host 200 via the secondfile set signaling (S30). Here, the second file set signaling may beformed of success/fail information corresponding to input/outputrequests for the plurality of files. However, one or more exampleembodiments of the inventive concepts are not limited thereto. Forexample, the second file set signaling may be variously formed of filerelated information. The host 200 parses bit data based on the secondfile set signaling from the storage device 100. For example, the storagedevice 100 may encode bit data (e.g., [01101100]) as a series of readsuccess and/or read failure messages, and then send the read successand/or read failure messages to the host 200, which may decode theseries of read success and/or read failure messages to determine the bitdata sent from the storage device 100.

Now a non-standard communication method using a read request will bedescribed with reference to FIGS. 5 to 7.

FIG. 5 is a diagram schematically illustrating the process of generatinga file set channel using a read request, according to at least oneexample embodiment of the inventive concepts. For example, the shadedblocks in FIG. 5 may represent read requests issued from the host 200 tothe data storage device 100. Blank blocks in FIG. 5 may indicateinstances in which no read request is sent for a particular file.Vertical positions of the blocks illustrated in FIG. 5 represent apoints in time (i.e., t1-tn) to which the blocks correspond, where ‘n’is a positive integer.

Referring to FIG. 5, a storage device 100 groups and stores logicalblock addresses OxXX, OxYY, OxAB . . . OxQQ of N files F1 to FN and diskinput/output requests “disk io” corresponding to the logical blockaddresses. For example, the storage device 100 may group and store thenumber of read requests generated, respectively, for logical blockaddresses OxXX, OxYY, OxAB . . . OxQQ of N files F1 to FN.

For example, during a first sequence Seq1, the storage device 100 stores(LBA1, 1), (LBA2, 1) . . . (LBAN, 1). During a second sequence Seq2, thestorage device 100 stores (LBA1, 1, 2), (LBA2, 1, 2) . . . (LBAN, 1, 2).During a third sequence Seq3, the storage device 100 stores (LBA1, 1, 2,3), (LBA2, 1, 2, 3) . . . (LBAN, 1, 2, 3).

In non-standard communication determiner 120 (refer to FIG. 1) of thestorage device 100, a file set channel is formed when a file set thathas been successfully recognized exists up to the third sequence Seq3.

Also, an application 220 (refer to FIG. 1) checks whether a file setchannel is formed successfully after the sequences Seq1 to Seq3. Here,whether a file set channel is formed successfully may be checkedaccording to transmitting and receiving of file set signaling which willbe described later.

At least one example embodiment of the inventive concepts may includeforming and/or generating a file set channel by recognizing a specificpattern of read requests for a file set.

FIG. 6 is a diagram showing a process of effectuating transmitting offile set signaling using a read request, according to at least oneexample embodiment of the inventive concepts. For example, the shadedblocks in FIG. 6 may represent read requests issued from the host 200 tothe data storage device 100. Blank blocks in FIG. 6 may indicateinstances in which no read request is sent for a particular file.Vertical positions of the blocks illustrated in FIG. 6 represent apoints in time (i.e., t1-tn) to which the blocks correspond, where ‘n’is a positive integer.

Referring to FIG. 6, in case of data transmission, an application 220generates (N+2) files, and the application 220 and the storage device100 may recognize addresses of the (N+2) files. Here, locations of thefiles thus generated need not be continuing. Locations on the files thusgenerated may not be restricted.

N files F1 to FN are used as a bit line for transmitting bit data, andthe remaining two files Ready and Tx are used to transmit data set tothe bit line. The application 220 issues a disk input/output request“disk io” via a read request read on each file.

According to one or more example embodiments, an input/output request“disk io” is made by the host 200 with respect to the file Ready inorder to inform the storage device 100 that the host 200 is ready totransmit a signal via non-standard communication. For example, accordingto one or more example embodiments of the inventive concepts, when thestorage device 200 transmits a particular input/output command to thestorage device 200 (e.g., a read request) for a particular file (e.g.,the ‘Ready’ file), the host 200 is signaling to the storage device 100that the host 200 is ready to begin non-standard communication, and thestorage device 100 interprets the signaling as an indication that thehost 200 is ready to begin non-standard communication.

A disk input/output request “disk io”, that is, a read request on filesfor a bit set of the files F1 to FN is issued. At this time, a storagedevice 100 stores files where the disk input/output request “disk io” isissued. Signal transmission is reported by issuing a disk input/outputrequest “disk io” for the file Tx. The storage device 100 views eachfile associated with the disk input/output request “disk io” as a bit.That is, the files are viewed as binary data (b101 . . . 1, (b000 . . .0, and (b111 . . . 1. At this time, N-bit, or (N+2)-bit, data istransferred by issuing a disk input/output request “disk io” for a fileset once. For example, according to one or more example embodiments ofthe inventive concepts, when the storage device 200 transmits aparticular input/output command to the storage device 200 (e.g., a readrequest) for a particular file (e.g., files F1-FN file), the host 200 issignaling to the host 200 is sending bits of data to the storage device100 as input/output signals, and the storage device 100 interprets thesignaling as bits of data being sent via non-standard communication. Forexample, sending a consecutive series of commands including a readrequest for file F1, no read request for file F2, a read request forfile F3, and no read request for file F4 may be interpreted as bit data(b1010) when the host 200 and storage device 100 are configured tointerpret read requests as corresponding to the bit ‘1’, and the absenceof read requests as corresponding to the bit ‘0’. Further, according toone or more example embodiments of the inventive concepts, when thestorage device 200 transmits a particular input/output command to thestorage device 200 (e.g., a read request) for a particular file (e.g.,the ‘Tx’ file), the host 200 is signaling to the storage device 100 thatthe host 200 is about to send, is currently sending or, alternatively,has completed sending bits of data via non-standard communication, andthe storage device 100 interprets the signaling as an indication thatthe host 200 is about to send, is currently sending or, alternatively,has completed sending bits of data via non-standard communication.

For example, as illustrated in FIG. 6, a read request for files Ready,F1 to FN, and Tx is issued to transmit first bit data (b101 . . . 1. Forexample, a read request read on files Ready and Tx is issued by transmitsecond bit data (b000 . . . 0. For example, a read request read forfiles Ready, F1 to FN, and Tx is issued by transmit second bit data(b111 . . . 1. As is discussed above, according to one or more exampleembodiments, the host 200 and storage device 100 may be configured suchthat, with respect to a non-standard communication, a read requestcorresponds to the bit ‘1’, and the absence of a read requestcorresponds to the bit ‘0’.

Meanwhile, a method of setting a bit ‘0’ or ‘1’ shown in FIG. 6 isillustrated as an example. According to one or more example embodiments,instead of using the bits ‘0’ and ‘1’ to refer to data that is not readrequested and data that is read requested, respectively, a bit ‘0’ maybe assigned to a file that is read requested, and a bit ‘1’ may beassigned to a file that is not read requested.

A file set signaling-based transmission method according to at least oneexample embodiment of the inventive concepts may transmit data byexpressing whether a read request on a file set exists, with a bit.

FIG. 7 is a diagram schematically illustrating a method of effectuatingreceiving of file set signaling using a read request, according to atleast one example embodiment of the inventive concepts. For example, thelight shaded blocks in FIG. 7 may represent read success indicationsissued from the data storage device 100 to the host 200, and the darkshaded blocks in FIG. 7 may represent read failure indications issuedfrom the data storage device 100 to the host 200. Blank blocks in FIG. 7may indicate instances in which no indication is sent for a particularfile. Vertical positions of the blocks illustrated in FIG. 7 represent apoints in time (i.e., t1-tn) to which the blocks correspond, where ‘n’is a positive integer.

A start of reception of file set signaling is informed by transmitting asignal, directing a success of a read request, from the storage device100 to an application 220. For example, the storage device 100 may send,to the host 200, a disk input/output request “disk io” to a logicalblock address corresponding to a file Ready.

The application 220 receives, from a storage device 100, signalsdesignating whether a read request on files F 1 to FN is successful. Forexample, sending a consecutive series of success/failure informationincluding a read success indication for file F1, no indication or a readfailure indication for file F2, a read success indication for file F3,and no indication or a read failure indication for file F4 may beinterpreted as bit data (b1010) when the host 200 and storage device 100are configured to interpret read success indications as corresponding tothe bit ‘1’, and no indication or a read failure indication ascorresponding to the bit ‘0’. For example, the storage device 100 sendsa bit ‘1’ to the application 220 via non-standard communications byindicating that a read request succeeded for a particular file. Incontrast, the storage device 100 sends a bit ‘0’ to the application 220via non-standard communications by indicating that a read request failedfor the particular file. The application 220 determines success/fail ofthe disk input/output request “disk io” using a return value of a “fileio api” of OS. According to one or more example embodiments of theinventive concepts, the application 220, as illustrated in FIG. 7,constructs bit data (b101 . . . 1 and (b000 . . . 0) by combiningindexes of files of which a file input/output request “file io”succeeds. Afterwards, as the application 220 receives a signaldesignating success of a disk input/output request “disk io” for a fileRx, an operation of effectuating receiving of file set signaling iscompleted.

A file set signaling-based reception method according to at least oneexample embodiment of the inventive concepts may receive data byexpressing whether a read request on a file set succeeds, with a bit.

Meanwhile, non-standard communication using a read request has beendescribed with reference to FIGS. 5 to 7. One or more exampleembodiments of the inventive concepts are applicable to non-standardcommunication using a write request.

FIG. 8 is a diagram schematically illustrating non-standardcommunication using a write request, according to at least one exampleembodiment of the inventive concepts. For ease of description, it isassumed that non-standard communication shown in FIG. 8 uses three textfiles 1.txt, 2.txt, and 3.txt each of which is stored in a storagedevice 100 by the cluster. Here, each cluster is formed of a pluralityof sectors indicated by logical sectors numbers (LSNs) illustrated inFIG. 8. For ease of description, it is assumed that a cluster is formedof four sectors. For example, the shaded blocks in FIG. 8 may representwrite update requests issued from the host 200 to the data storagedevice 100 for a corresponding file or logical sector number. Blankblocks in FIG. 8 may indicate instances in which no write update requestis sent for a corresponding file or logical sector number. Verticalpositions of the blocks illustrated in FIG. 8 represent a points in time(i.e., t1-tn) to which the blocks correspond, where ‘n’ is a positiveinteger.

Returning to FIG. 8, non-standard communication using a write requesteffectuates transmission of file set signaling by forming a file setchannel through a first update operation after storing of the files1.txt, 2.txt, and 3.txt and carrying out a second update operation.

The transmission of file set signaling will now be described below. Whenan application 220 of a host 200 (refer to FIG. 1) wants to effectuatenon-standard communication with a storage device 100, the application220 requests generation of the files 1.txt, 2.txt, and 3.txt to a filesystem 210 (refer to FIG. 1). The file system 210 generates the files1.txt, 2.txt, and 3.txt based on a request for the files 1.txt, 2.txt,and 3.txt of the application 220 and requests generation ofcorresponding write requests to a device driver 230 (refer to FIG. 2).Generation of the files 1.txt, 2.txt, and 3.txt may include allocationof logical addresses of the files 2.txt, and 3.txt. The device driver230 issues and transmits write requests, which the storage device 100can recognize, based on a request of the file system 210. Thus, thestorage device 100, which receives a write request for each of the files1.txt, 2.txt, and 3.txt from the device driver 230, may recognizelogical addresses of the files 1.txt, 2.txt, and 3.txt.

Afterwards, a first update operation is carried out to generate a fileset channel. During the first update operation, the application 220issues an update request for each of the files 1.txt, 2.txt, and 3.txtwith a specific pattern. The storage device 100 effectuates non-standardcommunication via the file set channel by recognizing the first updaterequest. Here, the file set channel may include the files 1.txt, 2.txt,and 3.txt.

Next, a second update operation is performed for transmission of fileset signaling. For example, a bit ‘1’ is assigned to a file to beupdated, and a bit ‘0’ is set to a file not to be updated.

For example, sending a consecutive series of update requests includingan update request for file 1.txt, no update request for file 2.txt, andan update request for file 3.txt, may be interpreted as bit data (b101),as illustrated in FIG. 8 when the host 200 and storage device 100 areconfigured to interpret update requests for a particular file ascorresponding to the bit ‘1’, and no update requests for a particularfile as corresponding to the bit ‘0’. The host 200 may communicate bitdata (b011) and (b110) in a similar manner as is also shown in FIG. 8.

In FIG. 8, an extension of the files 1.txt, 2.txt, and 3.txt may be“txt”. However, one or more example embodiments of the inventiveconcepts are not limited thereto.

At least one example embodiment of the inventive concepts may effectuatea transfer of file set signaling using a bit indicating whether anupdate operation on a file set is required.

FIG. 8 illustrates an example of an update operation on a cluster unitforming files 1.txt, 2.txt, and 3.txt for transmission of file setsignaling. However, one or more example embodiments of the inventiveconcepts are not limited thereto. For example, at least one exampleembodiment of the inventive concepts may be modified or changed suchthat an update operation is performed on at least one sector of acluster forming files 1.txt, 2.txt, and 3.txt for transmission of fileset signaling.

FIG. 9 is a diagram schematically illustrating non-standardcommunication using a write request, according to one or more exampleembodiments of the inventive concepts. Referring to FIG. 9, anon-standard communication method is different from that of FIG. 8 inthat a second update operation on only one sector of a cluster formingfiles 1.txt, 2.txt, and 3.txt is carried out for transmission of fileset signaling. For example, the shaded blocks in FIG. 9 may representwrite update requests issued from the host 200 to the data storagedevice 100 for a corresponding file or logical sector number. Blankblocks in FIG. 9 may indicate instances in which no write update requestis sent for a corresponding file or logical sector number. Verticalpositions of the blocks illustrated in FIG. 9 represent points in time(i.e., t1-tn) to which the blocks correspond, where ‘n’ is a positiveinteger.

In FIGS. 8 and 9, there is described an example in which 1-bit data istransferred using each of files 1.txt, 2.txt, and 3.txt. However, one ormore example embodiments of the inventive concepts are not limitedthereto. For example, n-bit data (n being an integer of 2 or more) maybe transmitted through each of the files 1.txt, 2.txt, and 3.txt. Forexample, sending a consecutive series of update requests including anupdate request for sector 1 of file 1.txt, no update request for file2.txt, and an update request for sector 1 of file 3.txt, may beinterpreted as bit data (b101), as illustrated in FIG. 9 when the host200 and storage device 100 are configured to interpret update requestsfor a particular file as corresponding to the bit ‘1’, and no updaterequests for a particular file as corresponding to the bit ‘0’. The host200 may communicate bit data (b011) and (b110) in a similar manner as isalso shown in FIG. 9.

FIG. 10 is a diagram schematically illustrating non-standardcommunication using a write request, according to one or more exampleembodiments of the inventive concepts. Referring to FIG. 10, anon-standard communication method is different from those of FIGS. 8 and9 in that a second update operation is carried out to transmit 2-bitdata via each of files 1.txt, 2.txt, and 3.txt. For example, the shadedblocks in FIG. 10 may represent write update requests issued from thehost 200 to the data storage device 100 for a corresponding file orlogical sector number. Blank blocks in FIG. 10 may indicate instances inwhich no write update request is sent for a corresponding file orlogical sector number. Vertical positions of the blocks illustrated inFIG. 10 represent points in time (i.e., t1-tn) to which the blockscorrespond, where ‘n’ is a positive integer.

As illustrated in FIG. 10, a cluster is formed of four sectors S1 to S4.Two bits of each of the sectors S1 to S4 are set to different values atan update operation. For example, during an update operation, a value ofthe first sector S1 is set to “11”, a value of the second sector S2 to“01”, a value of the third sector S3 to “10”, and a value of the fourthsector S4 to “00”. For example, sending a consecutive series of updaterequests including an update request for sector S1 of file 1.txt, anupdate request for sector 2 of file 2.txt, and an update request forsector 1 of file 3.txt, may be interpreted as bit data (b110101), asillustrated in FIG. 10, when the host 200 and storage device 100 areconfigured to interpret update requests for a particular file ascorresponding to specific pairs of bits in the manner described above.The host 200 may communicate bit data (b001001) and (111101) in asimilar manner as is also shown in FIG. 10.

A non-standard communication method according to at least one exampleembodiment of the inventive concepts may transmit 2-bit data througheach of the les 1.txt, 2.txt, and 3.txt.

As described above, FIGS. 5 to 10 are only embodiments on non-standardcommunication using “disk io” (read request or write request). At leastone example embodiment of the inventive concepts may form a file setchannel via a variety of methods of read or write requests or acombination thereof and transmits and receive file set signaling.Meanwhile, the file set signaling of at least one example embodiment ofthe inventive concepts may be named “cluster set signaling” or “sectorset signaling” according to a unit where a bit is transferred.

FIG. 11 is a flow chart schematically illustrating a non-standardcommunication of a host, according to at least one example embodiment ofthe inventive concepts. Now will be described a non-standardcommunication method with reference to FIGS. 1 to 11.

An application 220 of a host 200 requests generation of a plurality offiles to a file system 210 if non-standard communication between thehost 200 and a storage device 100 is required. In step S110, the filesystem 210 of the host 200 generates a set of files in response to arequest of the application 220.

In step S120, the host 200 transmits a predetermined or, alternatively,desired pattern of input/output requests corresponding to the set offiles to generate a file set channel. Here, the input/output requestsmay be formed of write or read requests. The file set channel is formedif the storage device 100 recognizes the predetermined or,alternatively, desired pattern of input/output requests transmitted fromthe host 200.

After generation of the file set channel, in step S130, the host 200transmits to the storage device 100 the input/output requestscorresponding to the set of files to transfer bit data. Each of theinput/output requests corresponding to the set of files may be viewed asat least one bit to be transmitted. Step S130 may be iterated totransfer bit data after generation of the file set channel.

A non-standard communication method according to at least one exampleembodiment of the inventive concepts may transmit bit data usinginput/output requests corresponding to a set of files.

FIG. 12 is a flow chart schematically illustrating a non-standardcommunication of a host, according to one or more example embodiments ofthe inventive concepts. Now will be described a non-standardcommunication method with reference to FIGS. 1 to 10 and 12.

A host 200 generates a set of files for non-standard communication(S210). Afterwards, the host 200 transmits a predetermined or,alternatively, desired pattern of input/output requests corresponding tothe set of files to generate a file set channel. The file set channel isformed if a storage device 100 recognizes the predetermined or,alternatively, desired pattern of read requests transmitted from thehost 200 (S220). After generation of the file set channel, the host 200transmits to the storage device 100 the read requests corresponding tothe set of files to transfer bit data (S230). Each of the read requestscorresponding to the set of files may be viewed as at least one bit tobe transmitted. Step S230 may be iterated to transfer bit data aftergeneration of the file set channel.

A non-standard communication method according to at least one exampleembodiment of the inventive concepts may transmit bit data using readcorresponding to a set of files.

FIG. 13 is a flow chart schematically illustrating a non-standardcommunication of a host, according to one or more example embodiments ofthe inventive concepts. Now will be described a non-standardcommunication method with reference to FIGS. 1 to 10 and 13.

A host 200 generates a set of files for non-standard communication(S310). A set of files may be written at a storage device 100 by thecluster (S320); therefore, the host 200 and the storage device 100recognize logical addresses on the set of files. Afterwards, the host200 transmits a predetermined or, alternatively, desired pattern ofupdate (or, write) requests corresponding to the set of files togenerate a file set channel (S330). The file set channel is formed ifthe storage device 100 recognizes the predetermined or, alternatively,desired pattern of update requests transmitted from the host 200 (S330).After generation of the file set channel, the host 200 transmits to thestorage device 100 the update requests corresponding to the set of filesto transfer bit data (S340). Each of the update requests correspondingto the set of files may be viewed as at least one bit to be transmitted.Step S340 may be iterated to transfer bit data after generation of thefile set channel.

A non-standard communication method according to at least one exampleembodiment of the inventive concepts may transmit bit data using writecorresponding to a set of files.

FIG. 14 is a flow chart schematically illustrating a non-standardcommunication of a storage device, according to at least one exampleembodiment of the inventive concepts. Now will be described anon-standard communication method with reference to FIGS. 1 to 10 and14.

A storage device 100 receives first input/output requests correspondingto a set of files for a file set channel (S410). The storage device 100determines whether a pattern of the first input/output requests is apredetermined or, alternatively, desired pattern (S420). The storagedevice 100 determines execution of non-standard communication if thefirst input/output requests having the predetermined or, alternatively,desired pattern are received. At this time a file set channel for thenon-standard communication may be formed.

Afterwards, the storage device 100 receives second input/output requestscorresponding to a set of files to receive bit data via file setsignaling (S430). The storage device 100 interprets the secondinput/output requests received via the file set channel as bit datatransmitted from a host 200 (S440).

A non-standard communication according to at least one exampleembodiment of the inventive concepts may receive bit data based oninput/output requests corresponding to a set of files.

FIGS. 12 and 14 describe a non-standard communication method using fileset signaling. The non-standard communication method of at least oneexample embodiment of the inventive concepts may be used to issue avendor command.

FIG. 15 is a flow chart schematically illustrating a method of executinga vendor command using file set signaling, according to at least oneexample embodiment of the inventive concepts. Now will be described amethod of executing a vendor command with reference to FIGS. 1 to 15. Anon-standard communication channel between a storage device 100 and ahost 200 is opened using a file set channel (S510). The host 200 issuesa vendor command for management of the storage device 100, and transmitsthe vendor command to the storage device 100 via file set signaling(S520). The storage device 100 parses the vendor command transferred viathe file set signaling to execute an operation corresponding to theparsed vendor command (S530). After an operation on the vendor commandis ended, the storage device 100 provides the host 200 with vendorcommand complete information via the file set signaling.

A vendor command may be, for example, a command that is specific to aparticular vendor or model of the host 200 and/or the storage device100.

A vendor command executing method according to at least one exampleembodiment of the inventive concepts may transmit a vendor command forfile set signaling.

Examples of devices according to one or more example embodiments of theinventive concepts will now be discussed below. One or more exampleembodiments of the inventive concepts are applicable to any electronicdevice using a micro SD card.

FIG. 16 is a block diagram schematically illustrating a mobile device 20according to at least one example embodiment of the inventive concepts.Referring to FIG. 16, a mobile device 20 incorporates an applicationprocessor 24 that is configured such that a micro SD card 22 is embeddedor inserted. Here, the micro SD card 22 is formed of a storage device100 shown in FIG. 1, and the application processor 24 is formed of ahost 200 shown in FIG. 1. Non-standard communication between the microSD card 22 and the application processor 24 may be effectuated usingfile set signaling.

An operating system installed on a general mobile device does not granta root authority to an application. In this case, the application maynot issue a command for executing firmware update, even though a memorycard (e.g., SD card, micro SD card, MMC, eMMC, etc.) has a firmwareupdate function.

In contrast, the mobile device 20 according to at least one exampleembodiment of the inventive concepts performs firmware update on themicro SD card 22 without restriction because it effectuates non-standardcommunication using file set signaling, based on a normal input/outputrequest.

One or more example embodiments of the inventive concepts are applicableto an electronic device that recognizes Universal Flash Storage (UFS).

FIG. 17 is a block diagram schematically illustrating a mobile deviceaccording to one or more example embodiments of the inventive concepts.Referring to FIG. 17, a mobile device 30 incorporates at least one UFSdevice 32 and an application processor 34. Here, the UFS device 32 isformed of a storage device 100 shown in FIG. 1, and the applicationprocessor 34 is formed of a host 200 shown in FIG. 1. Each of the UFSdevice 32 and the application processor 34 includes a mobile physicallayer M-PHY for non-standard communication. Non-standard communicationbetween the UFS device 32 and the application processor 34 iseffectuated using file set signaling.

The mobile device 30 according to at least one example embodiment of theinventive concepts manages the UFS device 32 via non-standardcommunication using file set signaling without communicationrestriction.

One or more example embodiments of the inventive concepts are applicableto an electronic device that uses a main memory.

FIG. 18 is a block diagram schematically illustrating a computing system40 according to at least one example embodiment of the inventiveconcepts. Referring to FIG. 18, a computing system 40 includes a centralprocessing unit 41, a memory module 42, a memory controller 43, and astorage device 44. The central processing unit 41 controls an overalloperation of the computing system 40. The memory module 42 is formed ofa plurality of memory chips 41-1 to 42-n. As illustrated in FIG. 18,each of the memory chips 41-1 to 42-n is configured to have a structurewhere a plurality of DRAM (or PRAM) chips are stacked. Here, each of theplurality of DRAM chips may encompass at least one master chip M and atleast one slave chip S.

The at least one master chip M and the at least one slave chip S maytransmit and receive signals via through silicon via (TSV). The masterchip may exchange a clock signal CLK, a command/address signal CA, anddata DQ with the memory controller 43. The master chip may transfer asignal from an external device to the slave chip via TSV or provide thememory controller 43 with a signal output from the slave chip.

The central processing unit 41 and the memory controller 43 areconfigured to effectuate non-standard communication using file setsignaling according to at least one example embodiment of the inventiveconcepts. For example, the central processing unit 41 may have thestructure and operation described above with respect to FIGS. 1-15 forthe host 200, and the storage device 44 may have the structure andoperation described above with respect to FIGS. 1-15 for the datastorage device 100.

One or more example embodiments of the inventive concepts are applicableto a solid state drive (SSD).

FIG. 19 is a block diagram schematically illustrating a solid statedrive according to at least one example embodiment of the inventiveconcepts. Referring to FIG. 17, a solid state drive (hereinafter,referred to as SSD) 1000 includes a plurality of nonvolatile memorydevices 1100 and an SSD controller 1200.

Each of the nonvolatile memory devices 1100 may be a NAND flash memory,a vertical NAND flash memory (VNAND), a NOR flash memory, a resistiveRAM (RRAM), a phase-change RAM (PRAM), a magnetoresistive RAM (MRAM), anSTT-RAM (Spin Transfer Torque Random Access Memory), or the like. Also,each of the nonvolatile memory devices 1100 may be implemented to have athree-dimensional array structure. The inventive concepts are applicableto not only a flash memory device where a charge storage layer is formedof a floating gate, but also a charge trap flash (CTF) memory where acharge storage layer is formed of an insulation film.

The nonvolatile memory devices 1100 are implemented to be provided withan external high voltage VPPx optionally. The SSD controller 1200 isconnected to the nonvolatile memory devices 1100 through a plurality ofchannels CH1 to CHi (i being an integer of 2 or more). The SSDcontroller 1200 includes one or more processors 1110, a buffer memory1220, an ECC block 1230, a host interface 1250, and a nonvolatile memoryinterface 1260. The SSD controller 1200 is configured to performnon-standard communication using file set signaling with an externalhost.

The buffer memory 1220 stores data needed to drive the SSD controller1200. According to one or more example embodiments of the inventiveconcepts, the buffer memory 1220 may include a plurality of memory lineseach of which stores data or a command. In FIG. 19 the buffer memory1220 is illustrated as being included in the SSD controller 1200.However, one or more example embodiments of the inventive concepts arenot limited thereto. The buffer memory 1220 may be placed outside of theSSD controller 1200. The ECC block 1230 is configured to correct anerror of data used at an input/output operation. Although not shown inFIG. 19, a code memory may be further included to store code data neededto drive the SSD controller 1200. The code memory may be implementedwith a nonvolatile memory device.

The host interface 1250 provides an interface with an external device.The nonvolatile memory interface 1260 provides an interface with thenonvolatile memory devices 1100.

The SSD 1000 according to at least one example embodiment of theinventive concepts may effectuate non-standard communication withoutrestriction of the host, for example, in the manner described above withrespect to FIGS. 1-15.

One or more example embodiments of the inventive concepts are applicableto an eMMC (e.g., an embedded multimedia card, moviNAND, iNAND, etc.).

FIG. 20 is a block diagram schematically illustrating an eMMC accordingto at least one example embodiment of the inventive concepts. Referringto FIG. 20, an eMMC 2000 includes one or more NAND flash memory devices2100 and a controller 2200.

The NAND flash memory device 2100 is a single data rate (SDR) NAND flashmemory device or a double data rate (DDR) NAND flash memory device. Or,the NAND flash memory device 2100 is a vertical NAND flash memory device(VNAND).

The controller 2200 is connected to the NAND flash memory device 2100via a plurality of channels. The controller 2200 includes one or morecontroller cores 2210, a host interface 2250, and a NAND interface 2260.The controller core 2210 may control an overall operation of the eMMC2000. The host interface 2250 is configured to perform an interfacebetween the controller 2200 and a host. The NAND interface 2260 isconfigured to provide an interface between the NAND flash memory device2100 and the controller 2200. According to one or more exampleembodiments of the inventive concepts, the host interface 2250 may be aparallel interface (e.g., MMC interface). According to one or moreexample embodiments of the inventive concepts, the host interface 2250of the eMMC 200 may additionally, or alternatively, be a serialinterface (e.g., UHS-II, UFS interface, etc.).

The controller 2200 is configured to effectuate non-standardcommunication using file set signaling with the host as described withreference to FIGS. 1 to 17. The controller 2200 may be implemented withat least one of a hardware configuration, and a configuration thatcombines hardware with software and/or firmware for non-standardcommunication.

The eMMC 2000 receives power supply voltages Vcc and Vccq from the host.Here, the power supply voltage Vcc (e.g., about 3.3 V) may be suppliedto the NAND flash memory device 2100 and the NAND interface 2260, andthe power supply voltage Vccq (e.g., about 1.8 V/3.3 V) may be suppliedto the controller 2200. According to one or more example embodiments ofthe inventive concepts, the eMMC 2000 may be optionally supplied with anexternal high voltage.

The eMMC 2000 according to at least one example embodiment of theinventive concepts may effectuate non-standard communication using fileset signaling according to a host request without restriction, therebyproviding convenient management, for example, in the manner describedabove with respect to FIGS. 1-15.

One or more example embodiments of the inventive concepts are applicableto Universal Flash Storage UFS.

FIG. 21 is a block diagram schematically illustrating a UFS systemaccording to at least one example embodiment of the inventive concepts.Referring to FIG. 21, a UFS system 3000 includes a UFS host 3100, UFSdevices 3200 and 3300, an embedded UFS device 3400, and a removable UFScard 3500. The UFS host 3100 may be an application processor of a mobiledevice. Each of the UFS host 3100, the UFS devices 3200 and 3300, theembedded UFS device 3400, and the removable UFS card 3500 maycommunicate with external devices through the UFS protocol. At least oneof the UFS devices 3200 and 3300, the embedded UFS device 3400, and theremovable UFS card 3500 may be implemented with a storage device 100shown in FIG. 1.

Meanwhile, the embedded UFS device 3400 and the removable UFS card 3500may perform communications using protocols different from the UFSprotocol. The UFS host 3100 and the removable UFS card 3500 maycommunicate through various card protocols (e.g., UFDs, MMC, SD (securedigital), mini SD, Micro SD, etc.).

One or more example embodiments of the inventive concepts are applicableto a mobile device.

FIG. 22 is a block diagram schematically illustrating a mobile device4000 according to at least one example embodiment of the inventiveconcepts. Referring to FIG. 22, a mobile device 4000 includes anapplication processor 4100, a communication module 4200, a display/touchmodule 4300, a storage device 4400, and a mobile RAM 4500. For example,the application processor 4100 may have the structure and operationdescribed above with respect to FIGS. 1-15 for the host 200, and thestorage device 4400 may have the structure and operation described abovewith respect to FIGS. 1-15 for the data storage device 100.

The application processor 4100 controls an overall operation of themobile device 4000. The application processor 4100 may be configured inthe same shown in FIG. 1. The communication module 4200 is implementedto perform wireless or wire communications with an external device. Thedisplay/touch module 4300 is implemented to display data processed bythe application processor 4100 or to receive data through a touch panel.The storage device 4400 is implemented to store user data. The storagedevice 4400 may be, but is not limited to, a memory card, an eMMC, anSSD, or an UFS device. The storage device 4400 may be implemented with astorage device 100 shown in FIG. 1.

The mobile RAM 4500 is configured to temporarily store data needed for aprocessing operation of the mobile device 4000.

The mobile device 4000 according to at least one example embodiment ofthe inventive concepts effectuates non-standard communication a fileset, thereby improving system performance overall.

One or more example embodiments of inventive concepts include issuing“disk io” to effectuate non-standard communication with a storagedevice. One or more example embodiments of the inventive concepts may beused regardless of hardware restriction and software restriction. Here,the hardware restriction may mean what may not be defined by thestandard interface communication protocol of a storage device, and thesoftware restriction may mean the situation where the standard protocolis not used due to a lack of the authority of a running application eventhrough the standard protocol exists.

The file set signaling method may be used under conditions: a transferof information to a storage device from an application, acquirement ofinformation from the storage device, a request of the application on acustom feature to the storage device.

One or more example embodiments of the inventive concepts are configuredto include an application and a storage device. Here, the storage deviceis applicable to all storage medium capable of generating “io”, such asHDD (hard disk drive), SSD (solid state drive), Flash Thumb drive, andso on. Also, if an application performs an input/output on a file usinga corresponding OS file io api, a corresponding OS file system uses acharacteristic of converting it into a sector address. Also, if anapplication directly appoints a sector address causing generation of“io” or names a sector address, such a sector address is used fornon-standard communication without modification.

At least one example embodiment of the inventive concepts may provide amethod capable of communicating with a storage device regardless of atype of a standardized interface of the storage device and a type of afile system installed on the storage device.

A memory system and/or a storage device according to at least oneexample embodiment of the inventive concepts may be packaged accordingto any of a variety of different packaging technologies. Examples ofsuch packaging technologies may include PoP (Package on Package), Ballgrid arrays (BGAs), Chip scale packages (CSPs), Plastic Leaded ChipCarrier (PLCC), Plastic Dual In-Line Package (PDIP), Die in Waffle Pack,Die in Wafer Form, Chip On Board (COB), Ceramic Dual In-Line Package(CERDIP), Plastic Metric Quad Flat Pack (MQFP), Small Outline (SOIC),Shrink Small Outline Package (SSOP), Thin Small Outline (TSOP), ThinQuad Flatpack (TQFP), System In Package (SIP), Multi Chip Package (MCP),Wafer-level Fabricated Package (WFP), Wafer-Level Processed StackPackage (WSP), and the like.

Example embodiments of the inventive concepts having thus beendescribed, it will be obvious that the same may be varied in many ways.Such variations are not to be regarded as a departure from the intendedspirit and scope of example embodiments of the inventive concepts, andall such modifications as would be obvious to one skilled in the art areintended to be included within the scope of the following claims.

What is claimed is:
 1. A communication method of an applicationprocessor comprising: generating a plurality of files; generating a fileset channel by transmitting a first pattern of input/output (I/O)requests to a storage device, the I/O requests being I/O requestscorresponding to files from among the plurality of files; andtransmitting first bit data to the storage device via the file setchannel, the first bit data being transmitted using file set signaling,the file set signaling including a second pattern of I/O requestscorresponding to first files from among the plurality of files such thateach file in the plurality of files represents a bit of the first bitdata.
 2. The communication method of claim 1, wherein, the applicationprocessor includes an application, and the generating a plurality offiles comprises: sending, from the application, a file I/O request to afile system, the file I/O request being a request for the files systemto generate the plurality of files.
 3. The communication method of claim2, further comprising: changing, at the files system, the file I/Orequest into a disk I/O request that is recognizable by the storagedevice.
 4. The communication method of claim 3, wherein the generating aplurality of files include generating, at the file system, the pluralityof files by a cluster unit.
 5. The communication method of claim 1,wherein the first and second patterns of I/O requests include readrequests.
 6. The communication method of claim 5, wherein thetransmitting first bit data includes transmitting the second pattern ofI/O requests such that the first files indicate a first bit value andsecond files indicate a second bit value different from the first bitvalue, first files being files from among the plurality files for whichthe second pattern of I/O requests includes a read request, second filesbeing files from among the plurality files for which the second patternof I/O requests does not include a read request.
 7. The communicationmethod of claim 6, wherein the transmitting bit data comprises:indicating to the storage device readiness to transmit the first bitdata by sending a read request corresponding to a ready file; andindicating to the storage device transmission of the first bit data bysending a read request corresponding to a tx file.
 8. The communicationmethod of claim 5, further comprising: receiving second bit data fromthe storage device via the file set channel, the second bit data beingreceived as a pattern of read indicators corresponding to files fromamong the plurality of files such that each file in the plurality offiles represents a bit of the second bit data, wherein the receivingsecond bit data includes interpreting the pattern of read indicatorssuch that third files indicate a third bit value and fourth filesindicate a fourth bit value different from the third bit value, thirdfiles being files from among the plurality files for which the patternof read indicators includes a read success indicator, fourth files beingfiles from among the plurality files for which the pattern of readindicators includes a read failure indicator.
 9. The communicationmethod of claim 8, wherein the receiving second bit data comprises:determining that the storage device is ready to transmit the second bitdata, in response to receiving, from the storage device, a readindicator corresponding to a ready file; determining transmission of thesecond bit data from the storage device, in response to receiving, fromthe storage device, a read indicator corresponding to a tx file.
 10. Thecommunication method of claim 1, wherein the first and second patternsof I/O requests include write requests.
 11. The communication method ofclaim 10, wherein the transmitting the first bit data comprises:transmitting the first bit data such that the file set signaling usesthe write requests, wherein the file set signaling includes transmittingbits by transmitting update requests for files from among the pluralityof files, such that each transmitted update request represent a bit, andwherein the update requests are transmitted in a unit of a cluster. 12.The communication method of claim 10, wherein the transmitting the firstbit data comprises: transmitting the first bit data such that the fileset signaling uses the write requests, wherein the file set signalingincludes transmitting bits by transmitting update requests for filesfrom among the plurality of files, such that each transmitted updaterequest represents a bit, and wherein the update requests aretransmitted in a unit of a sector.
 13. The communication method of claim10, wherein the transmitting the first bit data comprises: transmittingthe first bit data such that the file set signaling uses the writerequests, wherein the file set signaling includes transmitting bits bytransmitting update requests for files from among the plurality offiles, such that each transmitted update request represents at least twobits, wherein the update requests are transmitted in a unit of a clusterunit formed of a plurality of sectors that are continuing, and whereineach of the update requests for the files from among the plurality offiles include an update request on a sector, corresponding to the atleast two bits, from among the plurality of sectors.
 14. Thecommunication method of claim 1, wherein the file set signaling used totransmit the first bit data is a first file set signaling, and themethod further comprises: receiving bit data from the storage deviceusing a second file set signaling in which a manner in which data isrepresented is different from that of the first file set signaling. 15.The communication method of claim 1, further comprising: determiningwhether a non-standard communication with the storage device isrequired.
 16. A communication method of a storage device comprising:receiving, from a host, first input/output (I/O) requests correspondingto a plurality of files; recognizing a non-standard communication basedon the first I/O requests received; receiving second I/O requests on theplurality of files from the host after recognizing the non-standardcommunication; and interpreting the second I/O requests as bit datatransmitted from the host.
 17. The communication method of claim 16,further comprising: informing the host that a file set channel isformed, after recognizing the non-standard communication.
 18. Thecommunication method of claim 16, further comprising: informing the hostthat the non-standard communication is completed, after interpreting thebit data.
 19. The communication method of claim 16, further comprising:transmitting a file set signaling using I/O requests corresponding tothe plurality of files to the host, the file set signaling includingtransmitting a bits by transmitting an indicators indicating whether ornot a plurality of I/O requests succeed, such that each transmittedindicator represents a bit.
 20. A communication method of a hostincluding an application processor comprising: generating, at theapplication processor, a plurality of files; generating, at theapplication processor, a first pattern of input/output (I/O) requestssuch that the first pattern of I/O requests are recognizable by astorage device as a request to establish a file set channel between thehost and the storage device, the first pattern of I/O requests being I/Orequests corresponding to the plurality of files; establishing a fileset channel between the host and the storage device by transmitting thefirst pattern of I/O requests to the storage device; generating, at theapplication processor, a second pattern of I/O requests such that eachfile in the plurality of files represents a bit of bit data, the secondpattern of I/O requests being I/O requests corresponding to first filesfrom among the plurality of files; and transmitting the bit data to thestorage device via the file set channel by transmitting the secondpattern to the storage device.